Although FinderPop appears when i click on the unused space in the menu bar of any application, it doesn't work. I can't select anything within the menus. I am using OS 8.5.1 (international version).
I ran Conflict Catcher myself and located the conflict - it seemed to be a conflict between FinderPop and a control panel that controls one of the input kits included with MacOS 8.5.1 Taiwan. The name of the control panel is in Chinese and will appear as gibberish on your computer, but here it is: "¶rΩX¥ººz≈„•‹" sorry, as I'm sure that doesn't help you one bit . . .Anyway, by making FinderPop load AFTER that control panel I was able to get the pop-up menus to work again.
ΓÇó 27-October-98: Note that some people have problems when DataVizΓÇÖs MacLinkPlus CM plugin is installed. With or without FinderPop, but FinderPop may exacerbate it.
ΓÇó19-October-98: Clicking at (0, 0) ΓÇö i.e., the top left of the main screen ΓÇö will cause a FinderPop menu to drop down immediately.
ΓÇó05-August-98: Yet another UPDATE on WorldScript II and FinderPop ΓÇ£GrabbingΓÇ¥ problems with VM on: Peter Hartmann sez:
I am using the [FinderPopΓÇÖs] grab option with the JLK without any trouble since I removed a folder called Language Kit Additions from the system extensions folder. I think one of the files in it is the real culprit. This folder is installed by the JLK updater for OS8. It contains Japanese (J) and universal (Z) customization ressources for System 8.0, Quick Time 2.5 and LaserWriter 8.
ΓÇó09-June-98: UPDATE on WorldScript II/FinderPop problems. Peter Hartmann sez:
I recently found out that the real culprit of some of the JLK/World Script II problems is not WSII itself but the corruption of a file called"WorldScript II Resources". This file is automatically rebuilt if it is not found.
After a lot of investigation, I managed to solve a problem where AppleScript wouldn't do anything any more and instead of AppleScript syntax the Scripteditor showed class names. Maybe deleting this prefs file solved the FinderPop grabbing problem as well.
I earlier had a problem, where the machine crashed at startup at the exact moment the AppleScript extension loaded. Since I didn't realize the possibility of the "WorldScript II Resources" being at fault, I de- and reinstalled the JLK then (since I did not succeed by reinstalling AppleScript), which probably did not fix much more then removing this prefs file. (Kind of a fix-it-all-remedy…)
•28-May-98: Dr. Solomon’s AntiVirus, according to Paul Tavernise, appears to conspire with FinderPop to cause problems with mounting CD-R drives and opening the File Sharing Control Panel. UPDATE 06-Jun-98: Paul received an email from Dr. Solomon: “This particular problem was due to a bug in MacGuard. It was fixed in V7.78 release. It was also seen to happen on OSes other than system 8.x…”
ΓÇó13-May-98: WorldScript II ΓÇö after some stout detective work by Peter Hartmann, it turns out that this extension causes FinderPop to behave badly if you press ΓÇ£GΓÇ¥ to ΓÇ£Grab and DragΓÇ¥ an item from a FinderPop menu. IΓÇÖm looking into it (unfortunately I canΓÇÖt reproduce his crashes.)
ΓÇó QuicKeys 3.5.2 and FinderPop may not be 100% compatible. UPDATE 29-Apr-98: Jonathan Jacobs has narrowed this down to the QuicKeys Extension called ΓÇ£Pop-up MenuΓÇ¥. Removing this fixes the problem (but also means that any QK macros which use it will no longer work.)
The bug can apparently be alleviated by turning OFF the “Popup near…” items in the FinderPop “More Settings” dialog. (In my limited playing around with QK, I have not been able to reproduce this bug.)
ΓÇó There may also be problems with PPP Menus. As I canΓÇÖt use this, I canΓÇÖt debug it, so donΓÇÖt expect a quick resolution to this one.
ΓÇó Apple Data Detectors 1.0.2 requires you to use a US keyboard layout. DonΓÇÖt look at me, guv. UPDATE 11-May-98: Apple Data Detectors and non-US keyboard layouts news: According to Timo Orre: ΓÇ£I just want to add that if you use Contextual Menu Enabler extension version 1.0.2 (the previous version), it works fine for non-US keyboard layouts (but without the possibility to turn it off in applications). Unfortunately I dont know a publicly-accessible download site for it.ΓÇ¥
ΓÇó If you have a folder on your desktop whose name is the same as one of your mounted volumes, control-clicking on it results in a ΓÇ£ContentsΓÇ¥ submenu which refers to the disk, not the folder you clicked on. This appears to be a system software bug; IΓÇÖve filed a bug report at Apple.
• 68K support? HIGHLY UNLIKELY as I no longer have ready access to a 68K box and don’t have the spare time, either. Sorry about that…
ΓÇó At the risk of stating the obvious, if youΓÇÖre displaying the FinderPop Items embedded directly in the main popup menu and the FinderPop Items folder is empty, there will be no FinderPop Items added to the menu. (Other submenus, like the Processes and Desktop submenus, will be at their usual spots if you have enabled them.)
Some people who wished for only the ΓÇ£ContentsΓÇ¥ submenu without any extraneous FinderPop submenus can now have their wishes fulfilled. In a roundabout fashion ΓÇö the result of a happy accident.
ΓÇó FinderPop maintains two caches: one for menus it has built up, and one for icons. If you ever need to flush these caches, simply open the control panel, turn FinderPop off and then back on again immediately. The next time you Control-click, all FinderPopΓÇÖs menus and icons will be rebuilt from scratch.
ΓÇó FinderPop checks that its menu hierarchy caches are up-to-date by looking at the folder being cachedΓÇÖs modification date. Unfortunately, renaming an item in (for example) the ΓÇ£FinderPop Items FolderΓÇ¥ doesnΓÇÖt affect the folderΓÇÖs modification date; you can force the folderΓÇÖs mod date to change by creating a new folder and then immediately deleting it (Command-N, Command-Delete.)
• The Menu Manager will only display a maximum of 5 hierarchical menus at one time, so not all levels of a deep hierarchy can be displayed. I’m looking into extending this; one incredibly skanky method springs to mind…
ΓÇó Menus are now (1.3b0) built on-the-fly one level at a time, so you may sometimes notice a pause as you navigate into a large hierarchy. Menus are still cached, however, so you should only see this happening the first time you enter a particular folder (unless the folder is changing.)
ΓÇó Want to speed up FinderPopΓÇÖs building of a complicated menu hierarchy? Make sure the disk cache in the Memory control panel is set to some reasonable value -- for example, by clicking the ΓÇ£Use DefaultsΓÇ¥ button. 96K is not a reasonable value; my rule of thumb is to use one sixteenth of my physical memory up to a max of 2048K.
ΓÇó Copying/aliasing/moving from a tabbed folder doesnΓÇÖt appear to work. (The folder appears to close before the Finder can respond to the AppleEvents FinderPop sends to it.) At first glance, this appears to be a Finder bug, but IΓÇÖm looking into it! Latest: this is indeed a Finder bug; apparently to be fixed in 8.0.1 or 8.1 or whatever it is theyΓÇÖre calling it this week.
ΓÇó Holding down the Option Key while the Process submenu is active will display balloons which show the memory usage of a process. For some bizarre reason, you may need to depress it a few times, and move the mouse over to one edge or other of the menu item. A low-priority fix, but IΓÇÖll get around to it.
ΓÇó Holding down the mouse button during startup will disable FinderPop.
ΓÇó The ΓÇ£FinderPop Items FolderΓÇ¥ in the Preferences folder can itself be an alias.
ΓÇó FinderPop currently has no knowledge about which documents are openable by which applications, so it may be possible to ΓÇÿopenΓÇÖ a document using an inappropriate application. This will also be fixed in a future version (i.e., applications which canΓÇÖt open whatΓÇÖs selected in the Finder can be disabled or removed from FinderPop menus.)
ΓÇó Some people state that FinderPop fails to load with a ΓÇ£CouldnΓÇÖt Prepare Code FragmentΓÇ¥ error. I have not ever seen a case of this, but people to whom this has happened state that by getting FinderPop to load later (e.g., by renaming it to ΓÇ£~FinderPopΓÇ¥ or ΓÇ£zzFinderPopΓÇ¥) seems to fix this problem. Some helpful user sent me a Macsbug StdLog of his crash, and it looks like the system was unable to prepare ObjectSupportLib, an AppleScript library which is in the System File under Mac OS 8. Bizarre. IΓÇÖm investigating. This should be fixed in version 1.5f3; please contact me if you encouter this again!
ΓÇó Plotting colour icons in the FinderPop submenu -- things might look a tad strange in right-to-left text systems due to the skanky method I use to draw the icons for folders. As soon as I get around to locating a right-to-left MacOS 8 system, I'll do further testing. But be warned...
